-
Notifications
You must be signed in to change notification settings - Fork 243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Testable search #505
Testable search #505
Conversation
2a8b0a6
to
7e85ee4
Compare
If timestamp range search is selected the loop will only continue if range is valid. It does not make sense to check in functions below if range is valid since otherwise that code cannot be even reached
7e85ee4
to
806feb9
Compare
806feb9
to
a3de08f
Compare
move matcher to qdlt lib enable c++17 in qmake config The new code uses variant and optional added in c++17 standard while qmake config was setup restricted to c++11 enable tests only if gtest package found Set c++17 standard in cmake export class for windows linker Signed-off-by: Viktor Kopp <[email protected]>
a3de08f
to
bae0a27
Compare
@alexmucde any thoughts on this? in principle the PR is ready. |
Is c++1z the name for C++17? |
yes, this is the only way I was able to enforce it for "Build macOS (macos-13, Xcode_15.2)"-job. AFAIR, Win, Lin and Mac-14 were green if I use If we the project maintained only cmake build system, things would be simpler and cleaner. But I guess there is a reason you have to maintain both. |
The search dialog core functionality is moved into a separate class.
Added unit tests for the class. Without this change I do not believe it is possible to make any "reliable" improvements for the search.
The unit tests are so far run only locally. CI adjustments can be done later if this PR is merged
The "payload range" functionality is not implemented: it does not work in the
master
-branch and requirements are unclear.Since in this PR I use
optional
andvariant
I also switch on c++17 standard where these utils were introduced. If not acceptable, in principle code can be rewritten without them. See #501I tested the refactored search functionality on several dlt file manually, so far I did not see issues.